fix calculation of subsecond conversion in MIX or BIN mode #102
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fpistm
requested changes
Oct 5, 2023
FRASTM
force-pushed
the
fix_mix_bcd
branch
2 times, most recently
from
635d357
to
8d7d27c
Compare
Depending on the RTC mode, the SSR subsecond register and AlarmSSR differ when converted to/from a value in milliseconds Correcting the formula in GetTime, GetAlarm/StartAlarm functions. Clarify the use of getEpoch and setAlarmEpoch in BIN only mode. Signed-off-by: Francois Ramu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depending on the RTC mode, the SSR subsecond register and AlarmSSR
differ when converted to/from a value in milliseconds
Correcting the formula in GetTime, GetAlarm/StartAlarm functions.
Update description (README) for BINary only mode use with getEpoch and setAlarmEpoch